For more information on ECS configurations, see the Enhanced Charging Services Administration Guide.
If the configurations described in this section are not already available on the system, these must be configured.
|
2
|
|
4
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter.
|
IMPORTANT: Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.To enable and configure ECS functionality on the system you must obtain and install one of the following licenses:
|
l
|
[600-00-7526] Enhanced Charging Bundle 1 1k Sessions license
|
|
l
|
[600-00-7574] Enhanced Charging Bundle 2 1k Sessions license—to enable and configure Diameter and DCCA functionality with ECS
|
For information on how to install licenses, see the Managing License Keys section of the Software Management Operations chapter in the Administration and Configuration Guide.
At least one administrative user account that has ECS functionality privileges must be configured on the system. This is the account that is used to log on and execute ECS-related commands. For security purposes, it is recommended that these user accounts be created along with general system functionality administration.
|
l
|
Aside from having ECS capabilities, an ECS Administrator account also has the same capabilities and privileges as any other system-level administrator account.
|
|
l
|
You can also create system ECS user account for a config-administrator, operator, or inspector. ECS accounts have all the same system-level privileges of normal system accounts except that they have full ECS command execution capability. For example, an ECS has rights to execute every command that a regular administrator can in addition to all of the ECS commands.
|
|
l
|
Note that only Administrator and Config-administrator-level users can provision ECS functionality. Refer to the Configuring System Settings chapter of the System Administration and Configuration Guide for additional information on administrative user privileges.
|
|
l
|
ACS must be enabled in Optimized mode, wherein ACS functionality is managed by SessMgrs. The require active-charging optimized-mode command enables ACS in Optimized mode.
|
|
l
|
The require active-charging optimized-mode command must be a part of the boot configuration. If configured after booting, the configuration must be saved and the system rebooted for the change to take effect.
|
The following is the sequence of configurations necessary to source data to the inPilot application:
|
3
|
|
6
|
Save your configuration as described in the Saving the Configuration chapter.
|
|
l
|
P2P protocol detection must be activated only within rulebases used by the APNs for which P2P detection is applicable. P2P detection must not be applied to the rulebases used for APNs where such reporting is either not useful or is not possible.
|
attribute <attribute> { [ format { MM/DD/YY-HH:MM:SS | MM/DD/YYYY-HH:MM:SS | YYYY/MM/DD-HH:MM:SS | YYYYMMDDHHMMSS | seconds } ] [ localtime ] | [ { ip | tcp } { bytes | pkts } { downlink | uplink } ] priority <priority> }
|
l
|
For information on EDR format configuration and rule variables, refer to the EDR Format Configuration Mode Commands chapter of the Command Line Interface Reference.
|
show active-charging edr-format name <edr_format_name>
|
l
|
The rule-application routing command specifies the ruledef type. If not specified, by default, the system configures the ruledef as a charging ruledef.
|
|
l
|
For information on all the protocol types, expressions, operators, and conditions supported, refer to the Ruledef Configuration Mode Commands chapter of the Command Line Interface Reference.
|
Use the following configuration example to route traffic to the appropriate analyzer within each rulebase where the reporting is applicable.
show active-charging rulebase name <rulebase_name>
show active-charging charging-action name <charging_action_name>
file name <file_name> rotation volume <file_size_bytes> rotation time <file_complete_seconds> storage-limit <storage_limit_bytes> headers reset-indicator edr-format-name trap-on-file-delete compression gzip file-sequence-number rulebase-seq-num
cdr [ push-interval <interval> | remove-file-after-transfer | transfer-mode { pull | push primary { encrypted-url <enc_url> | url <url> } [ secondary { encrypted-secondary-url <enc_sec_url> | url <sec_url> } ] } + | use-harddisk ]
|
l
|
The <context_name> must be the context specified for accounting.
|
|
l
|
The cdr use-harddisk command is only available on the ST40 platform.
|
|
l
|
The cdr use-harddisk command specifies storing files on the hard disk. The reporting server will download these files through the SPIO interface on the SMC and will delete the files after successful retrieval.
|
|
l
|
The edr-format-name keyword must be configured to distinguish between different EDRs.
|
To manually push EDR/UDR files to the configured L-ESS, in the Exec mode, enter the following command:
cdr-push { all | local-filename <file_name> }
|
l
|
Before you can use this command, in the EDR/UDR Configuration Mode, the CDR transfer mode and file locations must be set to push.
|
|
l
|
<file_name> must be absolute path of the local file to push.
|
|
l
|
The user must be configured in the local context with administrative privileges to download and delete EDRs from the hard disk. The ftp nocli options restrict access to FTP only.
|
